Methods and apparatus for ingestion of legacy records into a mortgage servicing blockchain

ABSTRACT

Apparatus and methods for ingesting Legacy Records of mortgage loan servicing actions onto a Blockchain. The Blockchain is distributed to Participants in the Loan, such as the Borrowers, Regulators, Servicers, and Vendors. The present disclosure further provides a method for homogenizing a variety of Vendor Formats for inclusion on the Blockchain and memorializing execution of a smart contract on the Blockchain.

RELATED APPLICATION

This application claims benefit and priority to U.S. NonProvisional Patent Application No. 16/290,920 filed Mar. 3, 2019 and entitled METHODS AND APPARATUS FOR SERVICING AN OBLIGATION UTILIZING A BLOCKCHAIN which in turn claims priority to Provisional Application No. 62/637,693, filed Mar. 2, 2018, entitled “METHODS FOR SERVICING A LOAN UTILIZING A BLOCKCHAIN” which is incorporated herein in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates to methods for transferring legacy Mortgage Loan servicing records into a distributed ledger. More specifically, the present invention ingests legacy mortgage servicing records into a transparent Blockchain with no single point of failure.

BACKGROUND OF THE DISCLOSURE

Presently, loan servicing is a highly decentralized industry, featuring a labyrinth of heterogeneous standards and data formats across a wide variety of Participants including Borrowers, Servicers, Investors, Vendors, and other Persons involved in a loan servicing process.

As a result, even a small change in a status of a given Loan, or an event relating to the Loan, may take a significant amount of time to trickle down to every Participant involved in the Loan and the veracity of information is sometimes less than certain. This may result in various Participants to the Loan taking inconsistent actions based on outdated data. Moreover, Servicers and Investors lose a substantial amount of money each year due to missing loan documentation and regulatory penalties.

The systems generally used by loan Servicers (are fragile, rigid and) use highly outdated mainframe programming languages, many of which were first devised decades ago and provide fragile and rigid user interaction.

A user wishing to view a status of a Mortgage Loan, or to understand reasons behind certain events pertaining to the Mortgage Loan, presently may be charged Click Through fees to access their own data they also may need to be authenticated by a relevant loan service provider and retrieve data from a variety of different locations. Making matters even more complicated, data from different locations may not be consistent.

In addition, the loan servicing industry is a highly regulated one. Each user may be custodian of at least some potentially sensitive data that may be legally protected from disclosure or inadequate data protection.

Relatedly, not all users are permitted to view all data for a Mortgage Loan. For example, while a Borrower should generally be able to see every document pertaining to the Borrower's Loan, the Borrower may not be entitled to listen to a recording between a Lender and Legal Counsel concerning a loan. Similarly, a Vendor providing an appraisal should not have access to all data in the Mortgage Loan serving file, for example, the appraiser may not be privy to a Borrowers Social Security Number, or other Personal data.

Additionally, known loan servicing systems necessarily entail asymmetrical levels of trust. Some Participants may have financial incentives to modify certain documents (or may accidentally do so). Previous systems provide little or no deterrence to document modification.

Mortgage loan Servicers make matters worse by developing proprietary “add-on” technology that causes numerous disparate systems with a propensity to create process gaps and data integrity issues.

SUMMARY OF THE DISCLOSURE

Accordingly, the present invention provides methods and apparatus for moving away from legacy Mortgage Loan servicing platforms to a Blockchain platform. The methods and apparatus presented herein provide for orderly ingestion of legacy Mortgage Loan servicing records into a Blockchain system that provides transparent access to the records while regulating access to Loan Documents, providing safeguards against subsequent intentional or accidental document modification, tracking access to documents, eliminating Click-Through tracking and uniquely centralizing an inherently decentralized process. The present system also eliminates mechanisms for charging click through fees to Customers to access their own data ensures transparency in Mortgage Loan Obligation servicing processes.

The present invention utilizes Blockchain technology to provide Participants to a given Loan with an up-to-date certified correlation of actions executed, recordation of an identity of who executed respective actions, and certifying data, such as a ledger of actions taken on a Loan, as well as data associated with each action (e.g., time, place, user), thus ensuring that Participants: (a) can access only specific Loan Documents that a particular Participant is authorized to access; (b) cannot modify a previous action; and (c) can easily append new Loan Action to a Blockchain in a manner that links new Loan Action to previous events (e.g., a request for a new loan).

Additionally, in some embodiments of the present invention, an Ingestion Controller is provided to receive data in varying formats such as disparate formats utilized by disparate Participants and Vendors. Presently, varying formats are responsible for considerable delay, inaccuracy, and difficulty in Obligation tracking in a Mortgage Loan servicing process.

In some embodiments, the Ingestion Controller is configured to accept legacy mortgage servicing records in a Vendor Format and write the legacy records to a Blockchain pertaining to a Loan or other Obligation in a same Vendor Format as the legacy records was received. In other embodiments, an Ingestion Controller converts data from a Vendor Format to a standardized Servicer Format utilized by Blockchain and writes converted legacy records on the Blockchain as one or more Ledger Entries.

In still other embodiments, a Vendor is one of multiple known Participants. Each Participant may utilize a respective known (if still heterogeneous) data format. The Ingestion Controller is operational to convert data from a Vendor Format to a Servicer Format, and store the data in the Servicer Format on an associated Loan Blockchain. In some embodiments of the latter embodiment, the Ingestion Controller may translate data retrieved from a Loan Blockchain in a Servicer Format to a requested Vendor Format. Data retrieved from a Loan Blockchain may be transmitted to a Participant in one or both of the Servicer Format and the Vendor Format.

Preferred embodiments utilize a single Blockchain for all entries related to Mortgage Loan Servicing, although some embodiments may include multiple Blockchains to support an Obligation or Mortgage Loan servicing, such as a Vendor specific Blockchain or a function specific Blockchain (e.g. payment transaction Blockchain or loan owner Blockchain). A master Blockchain may track entries into other Blockchains included in a hierarchical or relational group of Blockchains.

In still another aspect, an Artifact and/or acknowledgement of the generation of an Artifact may be included in a Blockchain. An Artifact may include one or more of: a Smart Contract; an online submission with electronic signature verification; an image of a document or other quantifiable execution of an action may be stored in electronic format.

In some embodiments, the present invention may be practiced as a method for servicing a Mortgage Loan utilizing a Blockchain. A Mortgage Loan Obligation may be established based upon a transfer of funds from a first party to a second party and the Obligation may be secured with a Collateral Asset, such as mortgaged real property. A Blockchain is initialized on a computer server that is accessible via a digital communications network. The Blockchain may include multiple time sequential blocks, with each Block storing information related to the Obligation.

The Obligation may be memorialized in the Blockchain as a Mortgage Loan agreement. A first additional Block may be added to the Blockchain, with the first additional Block including a memorialization of the Mortgage Loan agreement. The Blockchain may be transmitted to a Loan Participant via the communication network.

The Blockchain may be configured to include Action data associated with a Loan Action in a Block in the Blockchain and appending the Action data to an end of the Blockchain as a second additional Block. An access right Block may specify which portions of a first additional Block and a second additional Block a Loan Participant may access and how.

A communications network such as the Internet may be used to transmit the Blockchain to the Loan Participant. The Blockchain may include blocks storing information that memorialize a Mortgage Loan Obligation, a first additional Block that memorializes the Mortgage Loan agreement, and subsequent blocks containing documents of records of actions taken. Access may be granted to the first additional Block, the second additional Block and subsequent blocks on the Block chain based upon the established access rights associated with a User.

In another aspect, notification of a payment related to a Mortgage Loan may be memorialized in the Mortgage Loan agreement and the notification of the payment may be stored in a third additional Block on the Blockchain. An access right for the Loan Participant may be established to the third additional Block. Access rights typically include one or more of the abilities for a Loan Participant to know that the Block exists but not be able to access information included in the Block, the ability to write to the Block and the ability to read the Block.

In some embodiments, an Artifact may be received quantifying an inspection of the Collateral Asset such as a mortgaged property. The Artifact may be stored in an additional Block and an access right established for the Loan Participant to the additional Block. An Artifact may, for example, include an appraisal of the Collateral Asset (mortgaged property) and be stored in still another Block with access rights established for the Loan Participant to the additional Block.

In another aspect, a quantification of an action, such as a correspondence regarding the Mortgage Loan agreement may be received and stored in a Block with an access right established for the Loan Participant to the Block. Action data may include, for example, one or more of: an identity of a Person executing the Loan Action and a resulting Loan balance following the Loan Action. In some embodiments, a previous Block of the Blockchain relating to the Loan Action may be cross referenced and a date for a follow-up action stored in the Blockchain. The Loan Action may be prompted by a Loan Servicing File that includes a record of at least one of: a work order, an email, correspondence and conversation recordation. A Loan Servicing File may be a Hardcopy File, and the Action data may further include information related to a physical location of the Hardcopy File. Action data may further include accessing information to retrieve an electronic facsimile of the Hardcopy File via the communications network. In addition, the Blockchain may include an electronic facsimile of a hardcopy Loan Servicing File. The electronic facsimile may be stored off Blockchain.

Some embodiments additionally include the step of executing a smart contract and storing the smart contract on the Blockchain or as an associated Off-Blockchain record. The Blockchain may be accessed via a network access device, such as a PC or a mobile smart device connected to a communications network, such as the Internet. In some embodiments, information stored on the Blockchain may be transmitted from a uniquely identified smart device.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, that are incorporated in and constitute a part of this specification, illustrate several embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure:

FIG. 1 illustrates an exemplary flowchart of the addition of a new Loan Action and associated new Action data to a Blockchain.

FIG. 2 illustrates an exemplary Blockchain with read access permissions defined.

FIG. 3 illustrates a mortgage-specific, non-limiting example of the interaction of two Participants with a Blockchain.

FIG. 4 illustrates three exemplary embodiments of an Ingestion Controller.

FIG. 5 illustrates an exemplary smart contract transfer of Investor status between a Company X and Company Y.

FIG. 6 illustrates apparatus that may be used to implement aspects of the present disclosure including executable software.

FIG. 7 illustrates a Block diagram of components involved in the ingestion of legacy Mortgage Loan servicing records into a Blockchain based Mortgage Loan servicing platform.

FIG. 8 illustrates additional method steps that may be used to implement the present invention.

FIGS. 9A-9B illustrate additional method steps that may be used to implement the present invention.

DETAILED DESCRIPTION

The present disclosure provides generally for methods and apparatus for instilling transparency, security, and auditability in a Mortgage Loan servicing process by ingesting Legacy mortgage loan serving records onto a Blockchain platform.

According to the present invention, a Participant to a Loan operates a computerized node to access a Blockchain memorializing executed actions that relate to a Mortgage Loan. When a Participant initiates a new Loan Action based on an event, such as receipt of a work order, the Participant creates a new Block on an associated Blockchain, encodes associated new Action data on the new Block, and transmits an updated Blockchain to Participants. A Participant may include a Person accessible via an automated network access device or an automaton, such as an Artificial Intelligence (“AI”) bot or the like.

In the following sections, detailed descriptions of examples and methods of the disclosure will be given. The description of both preferred and alternative examples though thorough are exemplary only, and it is understood that variations, modifications, and alterations are within the scope of the present invention. It is therefore to be understood that the examples do not limit the broadness of the aspects of the underlying disclosure as defined by the claims.

Although presented and described in view of Mortgage Loan Servicing, the present method may be applied to a broad field of dedication of one or more Assets by a first party to the benefit of a second party.

Glossary

“Action” as used herein, refers to an executed method step that is part of, or the entirety of a process.

“Artifact” as used herein refers to an item containing information or representative of information. Examples of Artifacts include one or more of: a document, a smart contract, an electronic communication, a voice recording, a video clip and a picture or other image data.

“Asset” as used herein, refers to an item with an associated value such as a real property, wherein ownership or use of the real property may be transferred from a first Person to a second Person.

“Blockchain” as used herein, refers to an implementation of an append-only, computerized linked data record (a “Block”) known to those in the art as a Blockchain, which is transmitted to, and stored upon a plurality of computerized nodes operated by a plurality of Participants upon an appending action. As used herein, Blocks on the Blockchain are generally numbered as B_(N), where _(N) is an integer. Where _(N) is not assigned a specific integer, B_(N) is presumed to be an arbitrary Block on the Blockchain; if _(N) is a specific integer, then B_(N) is presumed to be a corresponding Block (e.g., B₁ is the first Block on the Blockchain). Unless otherwise indicated, B_(N) occurs sequentially before B_(N+1). Where B_(N) and B_(M) are described separately, _(M) is presumed to be an integer not equal to _(N). A Block may be time stamped and secured and bound to each other using cryptographic principles (i.e. chain).

“Collateral” as used herein refers to an Asset, property or other item of value used to guarantee execution of an Action.

“Electronic File” as used herein, means any Loan Document captured in a digital format. By way of non-limiting example, an Electronic File may include one or more of: a smart contract, images, recording of phone calls, and electronically recorded data.

“Hardcopy File” as used herein, refers to any hard copy medium embodying a transaction or other action related to a Loan. By way of non-limiting example, a Hardcopy File may be one of: work order, promissory note, or documentation.

“Hash” as used herein means an encrypted value of a fixed length.

“Hashing” as used herein means that act of converting a string of unencrypted data of variable length into a string of encrypted data of a fixed length.

“Ingestion Controller” as used herein, refers to a computerized server in logical connection with a network access device and with software executable on demand, which is configured to accept New Loan Data from a Vendor and, in some embodiments, transmit desired blocks from the Blockchain to a Vendor.

“Loan Document” as used herein, means a text or image data quantified within boundaries and related to a Mortgage Loan.

“Loan Servicing File” as used herein, means one or both of a Hardcopy File and a Blockchain including multiple ledger entries containing one or more of: information, records of completed or anticipated Actions, Artifacts and documents related to a Loan.

“Mortgage Loan” as used herein, refers to provision of funds by a first party for the benefit of a second party for use by the second party with the provision of real property Collateral to the first party and agreed upon terms of repayment of the funds. A Mortgage Loan may be memorialized in a contract between the first party and the second party. Preferably the contract is quantified in a written document (electronic or hardcopy) and includes party identifiers, terms and conditions of the contract, and methods of meeting an Obligation (such as, for example, making a payment) and repayment of the loan.

“Obligation” as used herein refers to an agreed upon action or series of actions to be taken by or on behalf of an Obligor.

“Obligor” as used herein refers to a Person bound to perform an Action or series of Actions.

“Participants” as used herein, refers to Borrowers, Investors, Vendors, and Servicers that are parties to a Loan.

“Person” as used herein refers to a legal entity capable of ownership of an Asset and/or being bound to execute an Action.

“Servicer” as used herein refers to a Person tracking and facilitating fulfillment of Obligations by an Obligor. A Loan Servicer tracks fulfillment of Obligations related to a Loan type Obligation.

Referring now to FIG. 1, a list of exemplary method steps that may be executed in practicing some embodiments of the present invention are illustrated. At 100, a Blockchain is instantiated. At 101, first Block B₁ is instantiated. B₁ may include the Loan Parameters. By way of non-limiting examples, Loan Parameters may include a description of mortgaged property included in the Loan; terms for returning a loan amount, e.g., a schedule of payments and ultimate deadline to pay back loan amounts involved; Loan; amortization tables; names of parties to the loan; and information relating to the Property, such as an appraisal amount.

Blocks 102-108 illustrate steps involved in the processing of a new Loan Action. A Loan Action may include, but is not limited to, payments on the loan; phone calls between a Borrower and a Loan Servicer; audits on the loan; actions necessary to protect the Collateral of the loan (e.g., property appraisals); foreclosures; additional services offered based upon one or both of: The Loan and Collateral; and a default on a Loan payment or other Obligation.

At 102, the new Loan Action is instantiated based upon or relating to a Loan Servicing File, such as a Loan Servicing File. A Loan Servicing File may store a wide range of action initialization media. The media may include, but is not limited to, a promissory note; a letter requesting some action be taken on the loan; supporting documentation such as an appraisal of Collateral and an audio recording of a phone call or other conversation. A Loan Servicing File may be a Hardcopy File or an Electronic File. If a Loan Servicing File is a Hardcopy File, then the Hardcopy File might be digitized, leading to the creation of an Electronic File based on the Hardcopy File. If (_(N)-1) Block-creating actions have occurred on the Blockchain, then the instantiation of the new Loan Action results in the creation of a new Block, B_(N).

A new Loan Action may be associated with new Action data, which may include (but is not limited to) the name of a Person requesting and/or performing the new Loan Action; a type of Action; a time and date of the request; a time and date of requested performance; a deadline for complying with a request; in the case of a communication session, such as a phone call, video conference, a live interaction, a duration of the communication session; a reason for executing a Loan Action; a change to a pending Obligation, such as a loan balance, as a result of the Loan Action; a read permission for B_(N); and in the case of an Action taken in response to a request documented at Block B_(M), a cross-reference linking B_(N) to B_(M). Loan Action data may also include metadata.

In some embodiments a link is established in a platform of apparatus supporting a related Blockchain that links a related Loan Servicing File with B_(N) by adding to Action data information related to the Loan Servicing File. This may be particularly useful in situations with a Loan Action based upon content included in a Loan Servicing File. For example, possible, non-exhaustive options for generating a link may include one or more of: Action data includes location of a Hardcopy File 104; Action Data includes a private key to access all or part of a file 105; Action Data includes Blockchain file transfer protocol data (PFS) to store an electronic version correlating with a Hardcopy File on the Blockchain 106; Action Data does not include a location of a Hardcopy File; Action Data is appended to a Blockchain 108 and a Blockchain is published back to Participants 109.

Further, FIG. 1 is a non-limiting example illustrating a Loan Servicing File that is, at least initially, a Hardcopy File. At 104, new Action data includes a physical location of a Hardcopy File, such as by one or more of: serial number; file custodian identification; and repository. Association of a Hardcopy File with a Blockchain based electronic system may be used to serve as an intermediate step for a loan Servicer executing Action steps to modernize loan servicing database, and still keep some amount of information at a hardcopy data warehouse. By way of non-limiting example, a user opting to implement a method using step 104 includes on B_(N) that a promissory note underlying a loan is located in Warehouse 4, Room 120, File Cabinet 3. By way of another non-limiting example, if B_(N) stores Action data regarding a phone call with a borrower, B_(N) may indicate identification information and a file path for a computer server on which one or both of an audio recording and transcription of a phone call is stored. As discussed more fully below, a computer server includes a processor in logical communication with a storage medium storing executable code that is executable on command to cause the processor to execute method steps.

Block 105 illustrates another possibility for linking a hardcopy Artifact, document or file with Action data, by way of an Electronic File. At 105, the Electronic File is uploaded to secure data storage via a communications network, such as the Internet. Due to a potentially sensitive nature of an Electronic File (e.g. a file with content relating to Personally identifiable financial documents), the Electronic File may be encrypted. For example, encryption may be implemented via Rivest-Shamir-Adleman (“RSA”) cryptosystem for secure data transmission or another cryptography method for data transmission and/or storage. RSA cryptography is an asymmetric encryption scheme, comprising the use of a private and public key.

In some embodiments of the present invention, Participants receive a public key to allow encryption of information included in an Electronic File stored on a Blockchain. However, in some embodiments, at 105, only those Participants authorized to view an Electronic File receive an affiliated private decryption key. Accordingly, a Participant authorized to view B_(N) is provided with a mechanism to access to the Electronic File. Similarly, 106 allows a Participant authorized to view B_(N) to view the Electronic File directly on a Blockchain, if the particular Blockchain implementation utilized allows for file storage. Blocks 105 and 106 could also cover a Loan Action prompted by a Loan Servicing File that originates as an Electronic File. In some embodiments, an Electronic File stored B_(N) may not be associated with a Hardcopy File 107.

Entry of new Action data, including reference to the Loan Servicing File described by 103, may be aggregated and associated Action data is added to Block B_(N), which is appended 108 to the Blockchain.

In addition, the Blockchain may be published 109 to all Participants or to selected Participants. Publication is an important element of Blockchain technology, as it allows for the nonrepudiation of a given Block. In some embodiments, a Participant may possess a current copy of a Blockchain and yet the Participant may not have read access to one or more blocks included in the Blockchain.

Referring not to FIG. 2, an exemplary section of a Blockchain 200 is illustrated, including a Block's read permissions for a variety of examples of Participants. In this non-limiting example, the Blockchain illustrated includes five Blocks, 201-205. Pertinent classes of Participants in this example include Borrowers; Servicers; Investors 206A-206C; Regulators 207; and an Action Actor 206 executing an Action. B₁ 201 corresponds to an initialization of the loan. Data stored on B₁ may include an electronic copy of the promissory note; the original balance of the loan; the payment term; and the Collateral for the loan. The lines ending in dots demonstrate read access. For example, it may not be desirable to give every Participant one or both of read and read and write access to every Block. For example, a new Loan Action Actor 206, may not be provided read access to data in a Block that includes a promissory note and other sensitive information stored on B₁ 201. On the other hand, one or more Regulators 207 may be properly vetted and be provided audit authority to all Blocks based upon the Regulators' 207 interest in sensitive information. Additionally, one of the primary goals of the present disclosure is increasing transparency for one or more Participants, such as: Borrowers 206A, Servicers 206B, and Investors 206C. Accordingly, as demonstrated by FIG. 2, only Regulators 207 and Borrowers 206A, Servicers 206B, and Investors 206C may be provided access to B₁ 201.

A document B₂ 202 or other Artifact, may in this example, correspond to a Loan Servicing File initiating a request on behalf of a new Loan Action actor, which has access to view the document B₂ 202 it added to the Blockchain 200. A financial transaction B₃ 203, may in some examples, be linked to document 202 at B₂. Correspondence B₄ 204 may also be stored in a Block B₄. Correspondence may include hardcopy, electronic communication, facsimile, or other Artifact conveying information from a first Person to a second Person. Similarly, a record of a Call B₅ 205 is exemplary of another type of Blocks which may exist within the Blockchain 200 memorializing Actions arising from an Obligation, such as a loan. According to the present invention, a record of a call may include one or more of an audio file, a transcript of a conversation, a video file, or other record of an: in Person, telephonic or voice/video over IP (VOIP) conversation.

Records of other information and Artifacts may also be stored in a Block, such as, by way of nonlimiting example: scanned documents; e-signed documents; spreadsheets; receipts of payment; documents validating an identity; notary seal; appraisals; photographs; comparable property descriptions; proof of funds; evidence of income; biometric measurements, declarations of race and/or ethnicity, evidence of residency, evidence of citizenship; parties of interest; co-signers; guarantors; next of kin; insurance policies and/or summaries; and other information that may be memorialized or quantified in an electronic format and stored in a Block.

Referring now to FIG. 3, exemplary method steps are illustrated that may be executed in some embodiments of the present invention. The example illustrated generally relate to a pair of linked transactions related to a mortgage. At 300, a mortgage Servicer, which is a Participant, orders an inspection on Borrower's Property from another Participant, such as, for example, Property Appraiser.

At 301, as part of the process of ordering the inspection, Servicer records the inspection order on Blockchain as Block B_(N). The order constitutes an Action to commence a new Loan. The Action is associated with Action data 305. In this non-limiting example, the Action data 305 recorded on Block B_(N) includes the name of the employee at Servicer requesting the inspection; data of the order; deadline for inspection; reason for inspection; and instructions allowing all Participants to read B_(N). Once a new Loan Action and new Action data are recorded on new Block B_(N), the Blockchain 304 is transmitted to Participants. In some embodiments, Property Appraiser records a confirmation of receipt on new Block B_(N+1), or another Block linked to B_(N).

At 302, a Vendor who is a Property Appraiser conducts the ordered inspection. Upon completion of the inspection, at 303, Property Appraiser instantiates a new Loan Action on Block B_(M) (where _(M)>_(N)). This new Loan Action will have associated with a new Action data 306, pertinent information related to the inspection. This new Action data 306 recorded on Block B_(M) includes the name of the employee(s) at Property Appraiser who conducted the inspection and reviewed its results; the results of the inspection; association with Block B_(N); and read permissions for Borrower, Property Preservation, and Servicer.

Finally, the updated Blockchain is transmitted 304 to Participants with new Block B_(M). Notably, even those Participants who do not have read access will receive the updated Blockchain. Such Participants will (a) be aware that the Blockchain has been updated with new Block B_(M); and (b) be able to see the Hash value, previous Block Hash value, and nonce of B_(M). This is desirable to achieve the nonrepudiation trait of Blockchain.

In some embodiments, it may also be desirable to encode on the Block B_(M) data that all Participants can access. In the non-limiting example shown in FIG. 3, all Participants have read access to B_(N), which stores the inspection order, but only a limited subset of Participants have read access to B_(M), which stores the results of the inspection. Although such results may be confidential, it may nonetheless be desirable for a Participant that can read B_(N) to be aware that B_(M) contains the result of the inspection order stored at B_(M). Accordingly, the new Action data for B_(M) can also specify the read access of each element of new Action data for B_(M), and may allow read access to all Participants for the datum linking B_(M) to B_(N).

Again, the implementation set forth in FIG. 3 is merely a non-limiting example. In a generic situation, Property Appraiser could stand for any Vendor or other provider assisting a Loan Servicer, and the inspection could be any action taken in furtherance of the Loan.

Currently, a significant problem facing the loan servicing industry is a myriad of format types used by Vendors and Servicers in processing information. Many Vendors have their own proprietary data formats, which may render adding data 303 to the Blockchain 304 difficult.

Accordingly, referring now to FIG. 4, in some embodiments it may be desirable to configure a Ingestion Controller (discussed in more detail below) to assist in converting data to and from the proprietary formats of the various Participants (the “Vendor Format”). The Vendor Format is in contrast to a standardized format utilized by the Servicer, the Servicer Format. While this non-limiting example assumes that Servicer Format is ordinarily more desirable than Vendor Format, this is not required. At 400, a Vendor (such as, in FIG. 3, Property Preservation) desires to add new Action data to the Blockchain. The Ingestion Controller may be configured in one of at least three alternative ways.

Alternative A (as demonstrated in 401 and 404): at 401, the Vendor uploads to the Ingestion Controller new Action data in Vendor Format. At 404, Ingestion Controller instantiates a new Block on the Blockchain with the new Action data stored in Vendor Format. This Alternative may be desirable where a plurality of Vendors associated with the Loan, possibly along with Investors, Borrowers, and Servicers, use a same or similar data format to the Vendor Format. Alternative A may also be desirable if Vendor uses any proprietary encryption techniques and wants decryption to occur outside the Blockchain environment.

Alternative B (as demonstrated by 402, 403 and 405): at 402, the Ingestion Controller receives Legacy mortgage loan servicing records in a Servicer format and at 405, the Ingestion Controller instantiates a new Block on the Blockchain with the Action data stored in Servicer Format. In Alternative B, the work in converting the Action data to Servicer Format is done by Vendor.

Alternative C (as demonstrated by 401, 403, and 404): at 401, the Vendor uploads to the Ingestion Controller Action data in Vendor Format. At 403, the Ingestion Controller converts the data from Vendor Format to Servicer Format, and at 405, the Ingestion Controller instantiates a new Block on the Blockchain with the new Action data stored in Servicer Format. In Alternative C, the work in converting the new Action data to Servicer Format is done by the Ingestion Controller. Accordingly, Alternative C may be preferred desirable where a Loan is associated with limited, known Vendors whose respective Vendor Formats may be pre-programmed into the Ingestion Controller, allowing for ready conversion between the respective Vendor Formats and the Servicer Format. This allows each Participant to retain its respective proprietary format, while also providing a universal format (the Servicer Format) for Participants like Borrowers or Investors who may not have proprietary formats.

A significant advantage of the present invention is that it reconciles a present state of the loan servicing industry, which is simultaneously centralized and decentralized. While there is a central entity responsible for handling the day-to-day servicing of a Loan (described herein as the Servicer), the Servicer outsources a variety of tasks to Vendors. Borrowers and Investors may have their own respective interests in a Loan. However, during the lifetime of a given Loan, each of multiple Participants may change identities multiple times. For example, a Servicer that created B_(i) of the Blockchain may assign Servicer's rights and Obligations under an underlying contract to a different Servicer. In some embodiments, the present invention provides a standardization of loan servicing process on a Blockchain, with a smart contract protocol incorporated onto the Blockchain to facilitate contracts and/or other documents underlying an associated Loan process. A smart contract may include a self-executing contract with terms of agreement directly written in computer code. In some embodiments, a smart contract may be executed without a physical hardcopy.

Referring now to FIG. 5 some embodiments of the present invention are illustrated that include a smart contract protocol applied to the Blockchain. FIG. 5 demonstrates a non-limiting example of a smart contract for transferring an Investor role from a Company Y to a Company X. One pertinent portion of the Loan Blockchain is shown at 505, with read access for each Block demonstrated at 520. Note that 520 only shows presence or absence of read access for X and Y; other Participants such as Borrower may have read access to these blocks. Thus, Y is the Servicer and has read access to blocks B_(N−2) at 511 and B_(N−1) at 512, prior to any agreement to transfer the Servicer role.

At 501, X agrees to buy the underlying Loan from Y for $500. Since the underlying Loan is implemented using the present method on Blockchain 510, at 520 X and Y agree to implement the transfer on a smart contract. This smart contract constitutes a new Loan Action, and accordingly is recorded at 513, B_(N). X now becomes a Participant, and both X and Y have read access to B_(N).

The smart contract at B_(N) has new Action data corresponding to 512. In particular, in this non-limiting example, the smart contract is a program configured to (a) store Y's Investor access credentials (e.g., Y's secret key in an RSA cryptography scheme) 533; (b) receive in a third party account the $500 from X 534; (c) upon receipt of $500 from X, transfer Y's Servicer access credentials to X 535, wherein the access credentials may include secret RSA keys; and (d) transfer the $500 from the third party account to an account designated by X for receipt of the $500.

At 504, X pays $500 to a third party account. This event is recorded as a new Loan Action at 514 Block B_(N+1). This new Loan Action at 514 Block B_(N+1) may include an acknowledgement of a receipt of X's $500. At 505, both X and Y may be provided read access to B_(N+1).

Finally, the smart contract program itself executes and creates Block 515 B_(N+2). The associated new Loan Action 514 records and executes the transfer of Y's access credentials to X at 504. X now has read access to at least all blocks beginning with B_(N). In some embodiments, it may be desirable upon completion of this transfer to give X read access to all blocks preceding B_(N), and/or revoke Y's access credentials to the entire Blockchain. This method of assignment is highly desirable, as it provides an easy method to transfer data about the Loan to X, instead of the present environment, which involves hours of digging through data warehouses.

Referring now to FIG. 6 a controller 600 is illustrated that may be utilized to implement some embodiments of the present invention. The controller may be included in one or more of the apparatus described above, such as the Blockchain Server, and the Network Access Device. The controller 600 includes a processor unit 610, such as one or more semiconductor based processors, coupled to a communication device 620 configured to communicate via a communication network (not shown in FIG. 6). The communication device 620 may be used to communicate, for example, with one or more online devices, such as a Personal computer, laptop, or a handheld device.

The processor 610 is also in communication with a storage device 630. The storage device 630 may comprise any appropriate information storage device, including combinations of storage devices (e.g., hard disk drives and server farms), solid state drives, optical storage devices, and/or semiconductor memory devices such as Random Access Memory (RAM) devices and Read Only Memory (ROM) devices.

The storage device 630 can store a software program 640 (executable software code executable on demand) for controlling the processor 610. The processor 610 performs instructions of the software program 640, and thereby operates in accordance with the present invention. The processor 610 may also cause the communication device 620 to transmit information, including, in some instances, control commands to operate apparatus to implement the processes described above. The storage device 630 can additionally store related data in a database 650 and database 660, as needed.

In various embodiments, a controller 600 may be incorporated into a network access device such as a smart device (e.g. a smart phone or smart tablet); a Personal computer (PC), a network server, or specialized user interactive device. Controllers may also be incorporated into specialized equipment, such as a scanner or printer. Typically, the scanner or printer will be in logical communication with a distributed network, such as a wide area network (WAN), a virtual private network (VPN) and/or the Internet. A Blockchain will be stored on a server (Blockchain Server) including one or more controllers 600 with processors operative via executable software to perform the method steps described herein. Typically, the Blockchain Server will be accessible via a communications network via network access device with a controller executing executable software.

Referring now to FIG. 7, a system 700 of Blockchain ingestion components for ingestion of legacy mortgage servicing records into a Blockchain is illustrated. According to the present invention, Legacy Records 715 are generated by legacy mortgage servicing Participants 711-714, which typically include: users 711 (such as a broker); a customer 712; an investor 713; and a vendor 714 (such as a property appraiser, insurance agent, etc.). In general, the legacy system 717 does not include actions, such as comments, conversation and transactions in a history of loan activity included in legacy records 715, such actions are often absent from the Legacy Records 715. The legacy records will typically include documents and metadata associated with the documents. Legacy meta data may include a description of the document, parties involved, dates and the like.

In some embodiments, the Legacy Records 715 will be contained in a relational database. In some embodiments, the Legacy Records 715 are extracted from the relational database and parsed into multiple blocks that are entered into the Blockchain 701 as a Ledger Entries 702-704.

Each Leger Entry 702-704 is associated with a Hash pointer that points to a previous Ledger Entry 702-704 (Block). Each Ledger Entry 702-704 contains data that may be encrypted. In addition, a Hash pointer contains a Hash of data contained in the previous Ledger Entry 702-704. The Hash pointers provide a secure link between two blocks entered as Ledger Entries 702-704.

Onboarding of Legacy Records 715 via an Ingestion Controller 717 includes presentation of the Legacy Records 715 to the Ingestion Controller 717, the presentation may be accomplished via digital communication across a communications network 718, or via a storage medium, such as a storage disk, a solid state memory, tape of other device suitable for storage of digital data.

In general, the Ingestion Controller 717 receives the Legacy Records 715 and converts the Legacy Records 715 into formatted Legacy Records 715 which includes a format suitable for Blockchain entries. The Ingestion Controller 717 communicates formatted Legacy Records 715 to the Blockchain where the formatted Legacy Records 715 are stored as one or more Blockchain Entries 702-704.

In some embodiments, conversion of Legacy Records 715 associated with a Mortgage Loan includes parsing, or otherwise segmenting the Legacy Records 715 into logical portions that may each be entered into the Blockchain 701 as a Ledger Entry 702-704. Parsing may be according to one or more of: event; chronological order; segment size; event; mortgage Servicer; or other criteria. Each parsed segment of Legacy Record 715 is capable of being entered into the Blockchain and associated with a unique Hash and a unique Hash pointer. Some or all of the parsed segments are entered into the Blockchain 701 as Ledger Entries 702-704. A Hash pointer and a Hash may be associated with each Ledger Entry 702-704.

A Hash pointer is a data structure that is used to indicate where information is stored. The Hash pointer may be used to indicate where a parsed segment resides in the Blockchain 701. As discussed above, a Hash is an encrypted value of fixed length. In some embodiments, a first Block of ingested data may be used to create a genesis Block as a first Ledger Entry 702. Each subsequent Block entered as a Ledger Entry 703-704 will be associated with a new Hash that links to the Hash of the previous Ledger Entry 702-704. Each Block entered as a Leger Entry 702-704 may be traced back via the succession of Hashes to the genesis Block Ledger Entry 702. Some embodiments include Hashing that involves appending a Nonce to Hashed contents of a Block entered as a previous Ledger Entry 702-704 in the generation of a Hash.

Some embodiments may also include Legacy Records 715 associated with a Mortgage Loan that are treated as a single data unit. In such embodiments, the Legacy Records 715 associated with the Mortgage Loan are entered into the Blockchain as a single Ledger Entry 702-704 and associated with a single Hash and a single Hash Pointer. In such embodiments, a single Ledger Entry all includes omnibus Legacy Records ingested for a particular loan may be treated as a genesis Block or a first Ledger Entry 702 for that particular loan.

According to the present invention, a Blockchain 701 is therefore created that incorporates content from Legacy Records 715 for reference and contextual purposes. Accounting tracked on the Blockchain 701 may commence with a value or other terms entered into the Blockchain via the Legacy Records 715, but Blockchain verified accounting commences only with those transactions entered via Blocks as Ledger Entries 702-704.

In general, although Legacy Records 715 accurately reflect a state of a Loan as provided to the Blockchain, accounting verification benefits of Blockchain do not apply to events included in the Legacy Records 715 since Legacy Systems did not include the Blockchain platform and its associated benefits. However, once ingested to the Blockchain 701, some benefits are made available. Benefits that are made available with ingestion into the Blockchain may include ubiquitous transparency to users 707-710, such as a mortgage broker 707; a vendor 708 (such as a property appraiser); a Customer 709; an investor 710; and the like are not available via Legacy System 717 that previously housed and processed the Legacy Records 715.

Legacy Records 715 may be ingested in variously sized onboarding activities. For example, Legacy Records 715 pertaining to a single Mortgage Loan may be ingested, such as, for example, a Mortgage Loan originated by a mortgage broker that is passed over to the Blockchain system 700 for Mortgage Loan servicing tracking. In such cases, the Legacy Records 715 may not include even a single payment record, and accounting benefits associated with the Blockchain 701 will apply for the term of the Mortgage Loan, with the Legacy Records 715 including the parties to the Mortgage Loan transactions, terms of the Mortgage Loan and the like.

Other embodiments may include ingestion of Legacy Records 715 that include Legacy Records 715 relating to a volume of Mortgage Loans that includes tens, hundreds or more Mortgage Loans. Ingestion of Legacy Records 715 including a volume of Mortgage Loans will typically include records of past payments, a sequence of multiple Mortgage Loan Servicers, payment history, balance and related data that is not verified by the Blockchain 701. With the shift to Blockchain 701, legacy system users 711-714 that previously did not necessarily have transparency to events involving other legacy system users 711-714 may now be provided with transparency to all Mortgage Loan servicing events.

In another aspect, a system 700 of Blockchain ingestion will store some data in an Off-Blockchain database 705 such that access to confidential, sensitive or regulated data may be controlled, while one or more Ledger Entries 702-704 indicate that such Off Blockchain Data 705 exists. Typically, access to Off Blockchain Data 705 is controlled via metadata. In some embodiments, each access to the Off Blockchain Data 705 may be recorded on the Blockchain 701 as an event and memorialized as a Ledger Entry 702-704.

The present invention therefore provides historical Legacy Records 715 for visual purposes, but does not rely on Legacy Records for its own servicing event verification other than a transferred balance amount and some basic information fields, such as the mortgagor and Person responsible for repayment.

In some embodiments, Legacy Records 715 that have been processed by the Ingestion Controller 717 and entered into the Blockchain 701 as one or more Ledger Entries 702-704 is made available as historical records via a Blockchain interface 706 to one or more users, such as: a Broker 707; a Vendor 708 (such as an appraiser or a title company); a Mortgage Loan customer 709; and an investor 710. The same users may be granted access to view the mortgage servicing Blockchain 701 to view Ledger Entries 702-704, wherein the Ledger Entries generally commence after Legacy Records 715 have passed through the Ingestion Controller 717 and included in the Blockchain 701 as one or more Ledger Entries 702-704.

Still further, some embodiments may include portions of Legacy Records 715 that are stored as Off-Blockchain Data and accessible via the Blockchain 701. Storage of Legacy Records 715 as Off-Blockchain Data 705 allows for more efficient data management. Off-Blockchain Data may also include Loan Servicing Files.

In general, the present invention is functional to convert Legacy Records 715 from being stored in unwieldy and unverified relational database resources into a Blockchain 701 that is verified by its architecture and distributed ledgers. Once the Legacy Records 715 are entered as Ledger Entries 702-704, the Legacy Records 715 are protected by the Blockchain 701 from being manipulated or deleted going forward. In addition, the Blockchain 701 provides a human readable interface 706 for access to the Ledger Entries 702-704 and the Off-Blockchain Data 705 without the need to charge for through charges or other such click fees based upon a number of times a user 707-710 accesses the Ledger Entries 702-704 and the Off-Blockchain Data 705, thereby providing more efficient access to users 707-710 to mortgage servicing information and more certainty to budgeting of costs associated with the Mortgage Loan servicing.

Referring now to FIG. 8, method steps that may be implemented in some embodiments of the present invention are listed. At method step 801 a Blockchain Ingestion Controller may receive mortgage loan servicing legacy records. Receiving of the legacy records may be accomplished, for example, via an electronic communication of digital data, via a storage device such as a solid-state storage device, a disk drive, a magnetic tape or other medium for storage of digital data. The records may be for a single loan, such as in the case of a mortgage broker that initiates a loan and transfer it to the Blockchain system, or for a tranche of loans. For example, a first tranche may be received as a first file containing legacy records for 80 loans, and a second tranche may include a second file with legacy records for 50 loans. A tranche of legacy loan records may be organized according to a common trait. For example, a tranche may include a set of legacy records for loans in foreclosure, or a tranche may include a set of legacy records for jumbo mortgages, or other trait.

At method step 802, the received Legacy Records are parsed into one or more blocks, each block containing legacy records for a single loan. Parsing may be according to a predetermined criteria. For example, parsing into blocks may be made according to a chronological order of events, a timeframe of events, a transfer of mortgage servicer, or other discernable criteria. In some embodiments, all legacy records for a particular loan are included as a single block.

At method step 803, blocks of legacy records are placed onto the Blockchain. The blocks may be included as one or more Ledger Entries. For example, it is preferred for each Block to be entered as a new Ledger Entry.

At method step 804, each Ledger Entry is associated with metadata. The metadata may include alphanumeric data that may be accessed for use in logical processes associated with the Blockchain and/or Off-Blockchain data. Each Ledger Entry may include an item and metadata associates with the item. An item may include a wide variety of events, such as a mortgage loan payment, a phone call record, an email message, a change in a loan term, or other event. Metadata may describe the item and also be used to control access to the item. Essentially, most or all Participants will be authorized to see that the Ledger Entry is on the Blockchain, but only some Participants may be granted access to the item or associated Off-Blockchain data.

At method step 805, in some embodiments, logical processes may include controlling access to portions of the Blockchain based upon the metadata and/or controlling access to portions of the Off-Blockchain data based upon the metadata.

At method step 806, data associated with Legacy Records may be placed in Off-Blockchain storage. Off Blockchain storage may include artifacts, such as documents, or related data. The Off-Blockchain storage is effective in limiting the size of the Blockchain.

At method step 807, portions of the Off-Blockchain data may be associated with one or more particular Blockchain Ledger Entries.

At method step 808 content of one or more Ledger Entries may be transmitted to a Participant based upon a request to make the transmission and logic the accesses the Participant's credentials and the metadata.

At method step 809, content included in the Off-Blockchain data may also be transmitted to a Participant based upon logic that accesses the Participant's credentials and the metadata.

Referring now to FIGS. 9A and 9B, additional method steps that may be executed in practicing some embodiments of the present invention are illustrated. Beginning with FIG. 9A. at method step 901, an artifact is generated that is associated with a post Blockchain mortgage servicing event. Post Blockchain events include events that occur at a point in time subsequent to ingestion of the Legacy Records into the Blockchain. The post Blockchain mortgage servicing event is associated with the Ledger Entries containing Legacy Records of a same loan and Blockchain Blocks may be appended to the Blockchain as Ledger Entries for the loan. An identification of the loan may be accomplished via metadata linked to an associated Block. Post Blockchain mortgage servicing Ledger Entries will have all of the advantages discussed herein relating to security and verification, while Ledger Entries of Legacy will contain values not verified by the Blockchain.

A post Blockchain mortgage servicing event may include, by way of non-limiting example: a payment made against a loan balance; an audio recording of a conversation (such as a telephone call) related to a loan; a rate adjustment; a change in mortgage servicer; a change in an owner of the mortgage; a copy of a correspondence; a property appraisal; an insurance policy; an interest charge; an advance on a collateralized line of credit; a request for a loan payoff amount; a loan payoff; and almost any other exchange or interaction related to the servicing of a mortgage loan.

At method step 902, a Block suitable for entry onto a Blockchain is generated that memorializes the post Blockchain mortgage servicing event. Memorializing may include, one or more of: a copy of a correspondence, an image of a hardcopy document; a recording of a conversation; a transcription of a conversation; a log entry, such as a record of a meeting or a telephone call; a contact management or customer relationship management (CRM) software record; or other descriptor, scan, copy, or notation.

At step 903, a hash is associated with a Block (or other Leger Entry). The hash is an encrypted output of a fixed length. According to some implementations of the present invention, a hash a non invertible function, such that the hash may be used to map a set of inputs to a set of outputs (hash(s) —>p), where variable “s” and variable “p” are both strings. For a string “s”, application of the hash function, provides a new string “p”. The Hash function is a deterministic procedure such that for any given input value “s”, a same hash will produce a same output value (‘p”). The Hash function is utilized in post Blockchain Ledger Entries to verify integrity of data in a Block contained in the Ledger Entry. Based upon the premise that a hash of the original Block will always map to a same value with the same hash function, a Participant is enabled to efficiently use a hash of a Block contained in a Ledger Entry and compare it with a published hash of the Block. If the Block has been adulterated or changed in (even a single bit) a value returned by the hash function also be changed.

At step 904, in some embodiments, a Hash Pointer may be associated with the Hash. The Hash Pointer will contain an address of a previous Block and the Hash of the data inside the previous Block.

At step 905, a Block that contains one or both of an artifact and information that memorializes a post Blockchain mortgage servicing event is appended onto the Blockchain as a Ledger Entry.

At step 906, details that are included in a Block included as a Ledger Entry are transmitted to one or more Blockchain Participants. The transmission may be accomplished for example via a digital communications network, such and an Internet Protocol (IP) communications network.

Referring now to FIG. 9B, at step 907, an artifact that is associated with a post Blockchain mortgage loan servicing event is placed in an Off-Blockchain storage. Embodiments of Off-Blockchain storage include a server; a server farm, and IP accessed cloud storage.

At step 908 the artifact associated with a post Blockchain mortgage loan servicing event is associated with one or more Blocks appended to the Blockchain as Ledger Entries. An artifact may include, by way of non-limiting example, one or more of: may include, one or more of: a copy of a correspondence, an image of a hardcopy document; a recording of a conversation; a transcription of a conversation; a log entry, such as a record of a meeting or a telephone call; a contact management or customer relationship management (CRM) software record; or other descriptor, scan, copy, or notation.

At step 909, some or all of the contents of a Ledger Entry that includes a Block memorializing the post Blockchain mortgage servicing event is transmitted to a Participant. In some embodiments, the transmission may be predicated upon results of a logical process that accesses the Participant's credentials and metadata associated with one or both of the Block and the Ledger Entry. In some embodiments, the Ledger Entry may be synonymous with a Block included in the Ledger Entry.

At step 910, an artifact memorializing the post Blockchain mortgage servicing event is retrieved and transmitted from the Off-Blockchain storage to a Participant. In some embodiments, the transmission may be predicated upon results of a logical process that accesses the Participant's credentials and metadata associated with one or both of the Block and the Ledger Entry.

At step 911, some embodiments may include a generation of a log the records access to one or both of the Blockchain and the Off-Blockchain storage.

At step 912, Ledger Entries appended to multiple Blockchain Nodes are reconciled. Typically, reconciliation is accomplished via a consensus mechanism. The consensus mechanism may be embodied in an automated process that is executed via programmable code running on a controller.

A number of embodiments of the present disclosure have been described. While this specification contains many specific implementation details, there should not be construed as limitations on the scope of any disclosures or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the present disclosure. While embodiments of the present disclosure are described herein by way of example using several illustrative drawings, those skilled in the art will recognize the present disclosure is not limited to the embodiments or drawings described. It should be understood the drawings and the detailed description thereto are not intended to limit the present disclosure to the form disclosed, but to the contrary, the present disclosure is to cover all modification, equivalents and alternatives falling within the spirit and scope of embodiments of the present disclosure as defined by the appended claims.

The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. As used throughout this application, the word “may” be used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including but not limited to. To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures.

The phrases “at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted the terms “comprising”, “including”, and “having” can be used interchangeably.

Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in combination in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while method steps may be depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order, or that all illustrated operations be performed, to achieve desirable results.

Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order show, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the claimed disclosure.

In certain implementations, multitasking and parallel processing may be advantageous. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the claimed disclosure. 

What is claimed is: 1) A method of ingesting legacy loan data into a blockchain, the method comprising the steps of: a) receiving mortgage loan servicing legacy records into an ingestion controller, said legacy records comprising digital representations of an obligation established by a participant based upon a transfer of an asset said participant comprising at least one of: a borrower, an investor, a vendor and a servicer of the loan; b) via operation of the ingestion controller, parsing the legacy records into multiple blocks suitable for entry onto a blockchain accessible via a blockchain controller which may or may not be a same controller as the ingestion controller; c) via operation of the ingestion controller, placing the multiple blocks comprising legacy records onto the blockchain as corresponding ledger entries, at least one of the multiple blocks memorializing the obligation via a mortgage loan agreement; d) via operation of the ingestion controller, associating each ledger entry with metadata; e) via operation of one of the ingestion controller and the blockchain controller, controlling access to portions of each ledger entry based upon logical processes accessing the metadata; f) storing electronic artifact representative of a hardcopy file associated with the legacy records in an off-blockchain storage; g) associating the electronic artifact representative of a hardcopy file stored in off-blockchain storage with a particular ledger entry; h) recording a physical location of the hardcopy file comprising a location of a building containing the hardcopy file; i) recording the location storing the hardcopy file as action data in one of metadata associated with a first additional block on the blockchain, and in the first additional block on the blockchain; j) linking a loan action to action data, the loan action comprising at least one of: payments on the loan, phone calls between the borrower and a loan servicer, audits on the loan, actions necessary to protect the collateral of the loan, foreclosures, additional services offered based upon one or both of the loan and collateral, a default on a loan payment, and the action data comprising at least one of: the name of a participant requesting or performing a new loan action, a type of action, a time and date of the request, a time and date of requested performance, a deadline for complying with a request, data related to a communication session which can be by phone, video, live interaction or duration of the communication session, a reason for executing a loan action, a change to a pending obligation, a read permission for a block, an action taken in response to a request documented at a specific block, and cross-reference linking between blocks, said action data further comprising a private key that is used as a mechanism to permit access to the portion of the blockchain via the granted access rights; k) recording the loan action and the action data on the second additional block based on the electronic artifact; l) generating a third additional block comprising a record of a payment related to the obligation memorialized in the mortgage loan agreement, m) generating a fourth additional block memorializing an authentication of the electronic artifact including a visual inspection of the hardcopy file stored at the physical location, the authentication being conducted on a uniquely identified mobile smart device corresponding to the participant or the any other participant, n) establishing granted access rights to each of the first additional block, the second additional block, the third additional block, and the fourth additional block; and o) transmitting to the participant or the any other participant a portion of the blockchain authorized via the granted access rights. 2) The method of claim 1 additionally comprising the step of transmitting items associated with ledger entries and stored in the off-blockchain storage to the participant or any other participant, based upon the logical process accessing the metadata and participant credentials. 3) The method of claim 2 wherein the items transmitted are associated with the ledger entries for which content is transmitted to the participant or any other participant. 4) The method of claim 3 additionally comprising the step of generating an artifact associated with a post blockchain mortgage servicing event, said artifact related to a loan associated with the ledger entries for which content is transmitted to the participant or any other participant. 5) The method of claim 1 additionally comprising the step of generating a block suitable for appending onto a blockchain, the contents of the block memorializing a post blockchain mortgage loan servicing event. 6) The method of claim 5 additionally comprising the step of associating a hash with the block suitable for appending onto a blockchain. 7) The method of claim 6 additionally comprising the step of associating a hash pointer with the hash. 8) The method of claim 7 additionally comprising the step of appending the block suitable for appending onto a blockchain and comprising contents of the block memorializing a post blockchain mortgage loan servicing event to the blockchain as a new ledger entry. 9) The method of claim 8 additionally comprising the step of transmitting details contained in the new ledger entry to the participant or any other participant. 10) The method of claim 9 additionally comprising the step of placing a post blockchain artifact in the off-blockchain storage. 11) The method of claim 10 additionally comprising the step of associating the post blockchain artifact with the block appended to the blockchain, said block comprising content memorializing a post blockchain mortgage loan servicing event. 12) The method of claim 11, further comprising the step of transmitting the content of the ledger entry comprising the block with an artifact memorializing the post blockchain mortgage servicing event to a participant based upon the logical process accessing metadata and the participant's credentials. 13) The method of claim 12 additionally comprising the step of transmitting the artifact associated with the post blockchain mortgage loan servicing event and stored in the off-blockchain storage to the participant based upon the logical process accessing metadata and the participant's credentials. 14) The method of claim 13 additionally comprising the step of generating a log recording participant access to the blockchain. 15) The method of claim 13 additionally comprising the step of generating a log recording access by the participant or any other participant to the off-blockchain storage. 16) The method of claim 13 additionally comprising the step of reconciling ledger entries appended to appended to blockchain nodes. 17) The method of claim 16 wherein the step of reconciling the ledger entries is accomplished via a consensus mechanism across the nodes. 18) Apparatus for ingesting legacy data into a blockchain, the apparatus comprising: a) an ingestion controller comprising a processor and a digital storage, said digital storage comprising executable code, executable upon demand by the processor to cause the apparatus to: i) receive mortgage loan servicing legacy records into the ingestion controller said legacy records comprising digital representations of an obligation established by a participant based upon a transfer of an asset; said participant comprising at least one of: a borrower, an investor, a vendor and a servicer of the loan; ii) parse the legacy records into multiple blocks suitable for entry onto a blockchain; iii) place the multiple blocks comprising legacy records onto the blockchain as corresponding ledger entries; iv) associate each ledger entry with metadata; v) store electronic artifact representative of a hardcopy file associated with the legacy records in an off-blockchain storage; vi) associate the electronic artifact representative of a hardcopy file stored in Off-blockchain storage with a particular ledger entry; vii) record a physical location of the hardcopy file comprising a location of a building containing the hardcopy file; viii) record the location storing the hardcopy the as action data in one of metadata associated with a first additional block on the blockchain, and in the first additional block on the blockchain; ix) link a loan action to action data, the loan action comprising at least one of: payments on the loan, phone calls between the borrower and a loan servicer, audits on the loan, actions necessary to protect the collateral of the loan, foreclosures, additional services offered based upon one or both of the loan and collateral, a default on a loan payment, and the action data comprising at least one of: the name of a participant requesting or performing a new loan action, a type of action, a time and date of the request, a time related to a communication session which can be by phone, video, live interaction or duration of the communication session, a reason for executing a loan action, a change to a pending obligation, a read permission for a block, an action taken in response to a request documented at a specific block, and cross-reference linking between blocks, said action data further comprising a private key that is used as a mechanism to permit access to the portion of the blockchain via the granted access rights: x) control access to portions of each ledger entry based upon logical processes accessing the metadata; xi) store items associated with the legacy records in an off-blockchain storage; xii) associate the items stored in off-blockchain storage with particular ledger entries; and xiii) transmit content of ledger entries to a participant based upon a logical process accessing the metadata and participant credentials; and b) an off blockchain storage suitable for storing the electronic artifact and accessible by the participant or any participant as permitted by the granted access rights.
 19. The apparatus of claim 18 wherein the executable code, executable upon demand by the processor additionally causes the apparatus to generate a block suitable for appending onto a blockchain, the contents of the block memorializing a post blockchain mortgage loan servicing event. 20) The apparatus of claim 19 wherein the executable code, executable upon demand by the processor additionally causes the apparatus to transmit content of the block to a participant based upon the logical process accessing metadata and the participant's credentials. 